Examples: Protocol files

Here you can find examples of a log file, message file, and an activity protocol.

Log file Log.txt – Example (excerpt)
Message file Messages.txt

(incomplete)

Save matrix E:\Usability\Quickstart\oev_test.MZW not possible!!
Incorrect skim parameters, no assignment result calculated
No OD demand for any OD pair. Assignment is not possible.
Activity protocol [Version name].trc

The file usually saves one row per operation. Each row consists of 5 entries which are separated by TAB:

<Time> <Record code> <User> <RefObject> <Description>
  • <Time>

The <Time> field contains the timestamp of the execution (local time) in the format YYYY-MM-DD hh:mm:ss Generally, the appropriate entry is written before an operation is executed so that crashes can be allocated.

  • <Record code>

Field <Record code> may contain the following values:

Record code

Meaning

TRDO_S

Transaction in Do-Direction: Start

TRDO_E

Transaction in Do-Direction: End (successful, commit)

TRDO_C

Transaction in Do-Direction: Cancelled (cancel)

TRUNDO_S

Transaction in Undo-Direction: Start

TRUNDO_E

Transaction in Undo-Direction: End

TRREDO_S

Transaction in Redo-Direction: Start

TRREDO_E

Transaction in Redo-Direction: End

D

Command (in Do/Redo-Direction)

U

Command (in Undo-Direction)

F

File-I/O (Version, Network, Subnetwork, Database)

P

Procedure (Assignment, ...)

O

Changes to trace settings

C

Comment (user entry ) (Adding a comment to the activity protocol))

/

Continuation line

  • <Reference object>

Record code

Reference object

Transactions start/ end/ canceled

Empty

Commands that refer to a single network object

Name of the network object type + Blank + ExternalKeyString

Other commands

Empty

File I/O

File name, exceptions:

  • for Read Attributes via clipboard empty
  • for Import from several files empty

Procedure

Reference object(s) Procedures

Changes to trace settings

Empty

Comment

Empty

Continuation line

Empty

  • <Description>

Depending on the trace level, field <Description> contains variably detailed descriptions of the operations.

Record code

Trace level

Description

Transactions start/ end/ canceled

>0

<Name of transaction>

Create command

>1

Create

Edit command

2

Edit

3+4

Edit in the first row, in other rows each

<Attribute short name>: <old value> -> <new value>

(for all edited input attributes)

Multi-edit command

2

<Network object type> Multi-Edit

3+4

in the first row <Network object type> Multi-Edit, Attribute <Attribute short name>,

in any further row each

<ExternalKeyString>: <old value> -> <new value>

Delete command

2+3

Delete

4

Delete in the first row, in other rows each

<Attribute short name>: <old value>

(for all input attributes with a value different from the default value)

Other commands

>0

Individual descriptions

File I/O

>0

Save version to file / Save network / Save sub-network / Save database / Read version from file / Read network/database / Read network/database additively/ Read EDF / Read HAFAS / Read EMME / Read attributes

Procedure

>0

Consecutive number + Blank + Operation + Blank + Procedure / File

Changes to trace settings

All

Trace on Level X / Trace off / New trace level X

Comment

All

Text entry by user

Example of an activity protocol of level 4: